Set kcons index to -1 (i.e., acquire all device indexes).

This reverts part of the previous changeset, which prevented
console=tty0 from doing the obvious thing in a domU guest
(i.e., send output on the virtual console). This is because
the tty index ends up being 1.

I don't think setting the index to other than -1 really
buys us anything anyway. Any other driver that specifies
a name that conflicts with us will almost certainly set their
index to -1, so we cannot avoid conflicts by choosing a
more restrictive (singleton) value.

Signed-off-by: Keir Fraser <keir@xensource.com>

diff --git a/linux-2.6-xen-sparse/drivers/xen/console/console.c b/linux-2.6-xen-sparse/drivers/xen/console/console.c
index 3b106f820443c651a65543ee7dc683acc845c1ea..0866ee58dd3544769a7d1e1e5ee750ec4f58eb7b 100644 (file)
--- a/linux-2.6-xen-sparse/drivers/xen/console/console.c
+++ b/linux-2.6-xen-sparse/drivers/xen/console/console.c
@@ -213,9 +213,6 @@ static int __init xen_console_init(void)
                return __RETCODE;
        }
 
-       /* We only bind to one device index (-1 means all indexes). */
-       kcons_info.index = xc_num;
-
        wbuf = alloc_bootmem(wbuf_size);
 
        register_console(&kcons_info);